home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.6 KB | 42 lines | [TEXT/GEOL] |
- Item forwarded by A33 to A34
-
- Item 6040771 26-Nov-89 19:46
-
- From: MOOF Rollin, Keith A
-
- To: MACAPP.TECH$ MacApp Technical
-
- Sub: UMacApp.TSomething.p
-
- Attn: Esha, David C Hands,PRT
- SentBy: Keith Rollin
- Reply to: UMacApp.TSomething.p
- David Hands,
-
- You write:
- --------
- In MacApp's Libraries folder there are several files named
- UMacApp.TSomething.p is it possible to access any of the TYPE's defined in
- these files? Specifically, I wanted to use TNewDocCommand which is defined in
- UMacApp.TApplication.p, but it appears to be private and unavailable to the
- application (I get a compile time error that TNewDocCommand is not declared).
- The unit USES UMacApp. Writing my own TNewDocCommand would be trivial, but
- I'd like to know why I can't use the pre-existing command.
- --------
-
- Technically, the reason why you can't reference TNewDocCommand is because it
- is not declared in the INTERFACE section of UMacApp.p. Neither will you be
- able to access anything declared solely in a file named UMacApp.TSomething.p.
- The mechanism for exporting a symbol to other units is to declare them in the
- INTERFACE section.
-
- I assume that the MacApp authors thought that there would not be a need for
- TNewDocCommand to be public. However, I think that they've since changed their
- minds. At least, the internal experimental version of MacApp has those object
- public. I expect that you'll be able to access them in the final version of
- MacApp 2.0.
-
- - Keith Rollin
- - Apple Developer Technical Support
-
-